fix(vue-query): re-export core filter types - #11287
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughVue Query updates query and mutation filter type exports. It adds Vue-specific filter aliases for reactive and callback inputs, aligns them with core filter types, and adds type-level tests and a patch changeset. ChangesVue Query filter types
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR re-exports core filter types from Vue Query and adds focused type coverage; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 4 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@tanstack/vue-querycurrently shadows query-core’sQueryFiltersandMutationFilterswith Vue-specific reactive types. Wrapper libraries that typeQueryClientoperations such asremoveQueriestherefore cannot import the matching filters from the Vue package. This renames the Vue-specific types and restores the core exports.